[Update October 2019]
Our own mechanism is now deprecated in favor of the Idea Portal in the Community. We absolutely want you to continue to submit feedback about the platform, but this is now the intake mechanism of record. Thank you!
As we continue forward iterating on the ServiceNow platform, we always want to make our tools better and your experience as a developer better. As we plan future releases, we want to know what your pain points are so we can make them better.
Offline for Mobile As promised we will cover more of the Madrid mobile features. Today we will look at the ability to configure and use offline abilities in the new mobile application. Offline on mobile devices opens up the locations and types of applications that can be deployed to your workforce.
The offline mode must be installed by ServiceNow, which means you need to use HI to request the plugin for customer instances.
As we continue our lightning tour of new developer-facing features of the Madrid release, we touch on some that are not net-new but include relevant changes. Today’s post is one of these. The London release featured the first release of Flow Designer APIs that allowed for invoking Flows via JavaScript APIs. That capability has been beefed up in Madrid and we’ll look at that.
Server-Side Flow APIs The London release had two APIs, startAsync for Flows and SubFlows.
Virtual Agent The spotlight for today is Virtual Agent which was introduced in London. The developer blog has a previous post Virtual Agent (London) to get you familiar with the product so check it out first before you read on about the new changes in Madrid. On to the changes we go!
Condition builder One of the first and notable changes is the addition of the condition builder to many of the activities.
Wondering what Madrid release can do for you? Overall, the store release for Madrid is focused on delivering a better experience of managing store applications and plugins into a single application. In this post, I will walk you through two modules for “All available applications and My Company Applications”.
All Available Applications My Company Applications
All Available Applications This is a new module in Madrid release. You can search/install/manage plugins and store applications in a single view.
Mobile in Madrid One of my favorite things in Madrid is the changes to Mobile. This will be a multipart series as we have a great deal to cover. Right off the bat, there is a whole new native app in the iOS and Google Play stores. ServiceNow Agent is its name. The previous mobile app is now named ServiceNow Classic. This single App will be the basis for all of the new targeted applets and experiences you make for your users.
Much of the work for Flow Designer in the Madrid release has been towards achieving feature parity with Workflows. That is to say that any work that could previously be done in a Workflow could now also be done in Flow Designer. Here is one of those features.
Do Until Loops This is a common bit of logic that is needed in any programming context, and now it is available in Flows.
Payload Builder A handy new feature in Madrid is the payload builder. This allows for reasonably simple name-value pairs payloads to be crafted into a payload object. The ability to use the inputs combined with a payload builder lowers the bar for building dynamic integration actions.
You can see the Name-Value pair setup is pretty straight forward using the data pill setup that is now familiar in Flow/Action Designer.
One of the things that I personally enjoy exploring each release is what has changed in the Automated Test Framework. This is a capability that I love and I like watching it improve to the point where organizations can capture ever more of their testing needs with it. Let’s look at some of what is new in Madrid.
Parameterized Tests One of the impediments to using the ATF at scale has been the handling of large quantities of test data.
Decision Tables The first feature in Madrid I am going to highlight is Decision Tables. These decision tables are a place to store the decision logic for variable situations. Each decision table record (sys_decision) handles a single decision. Related lists are the decision inputs (sys_decision_input) and decision (sys_decision_question) records. Each decision record contains an answer.
Our example will be for routing after hours service calls. We take multiple inputs in the form of location, time of submission, and the service.
